home *** CD-ROM | disk | FTP | other *** search
- Path: informatik.tu-muenchen.de!fischerj
- From: fischerj@Informatik.TU-Muenchen.DE (Juergen "Rally" Fischer)
- Newsgroups: comp.sys.amiga.advocacy,comp.sys.amiga.misc
- Subject: Re: Walker vs. the $999 7200/75 w/4xCD!
- Followup-To: comp.sys.amiga.advocacy,comp.sys.amiga.misc
- Date: 3 Apr 1996 02:36:36 GMT
- Organization: Technische Universitaet Muenchen, Germany
- Distribution: world
- Message-ID: <4jso7k$jhl@sunsystem5.informatik.tu-muenchen.de>
- References: <eraugust-2803960910170001@sbdsk0838.sbrc.hac.com> <1350.6662T1401T2752@mbox.vol.it> <4jpcr3$6ni@valour.pem.cam.ac.uk> <4jpok5$bu4@serpens.rhein.de>
- NNTP-Posting-Host: hphalle5.informatik.tu-muenchen.de
- X-Newsreader: TIN [version 1.2 PL2]
-
- Michael van Elst (mlelstv@serpens.rhein.de) wrote:
-
- : It is. But all the RISC technologies depend on memory speed. If memory were
- : ultimatively slow then CISC were the way to go, the more you can do with the
- : single memory fetch, the better. Currently the memory technology can barely
-
- A CISC needs less memory acess ? well, less code memory-acess.
- however, that's far less than data-memory acess (for most software).
- so quite little instruction cache gives a lot help.
- But CISC doesn't need less data-memory acess, which is the one that cares.
-
- : keep up with CPU technology. Machines already need huge and expensive caches
- : (most Alphas have 2 or 4MByte cache, SGIs about the same) and we _may_ eventually
- : see the return of more CISCier CPUs. This doesn't mean that we see 68k or VAX
-
- well, what would CISCier mean ? that some operations only work on
- Akku and only CX can be used as counter ? ;)
-
- ------------------------------------------------------------------------
- fischerj@Informatik.TU-Muenchen.DE (Juergen "Rally" Fischer) =:)
-
-